chore(deps): update dependency netlify-cli to v21 #2908
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
added
dependencies
📊 Package size report No changes
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
renovate
bot
force-pushed
the
renovate/netlify-cli-21.x
branch
from
6f50316 to
45f64c8
Compare
renovate
bot
force-pushed
the
renovate/netlify-cli-21.x
branch
from
45f64c8 to
d640afa
Compare
serhalp
approved these changes
May 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^20.1.1->^21.0.1Release Notes
netlify/cli (netlify-cli)
v21.0.1Compare Source
Bug Fixes
v21.0.0Compare Source
⚠ BREAKING CHANGES
netlify-lambdapackage (#7236)The netlify-lambda NPM package was deprecated in Feb 2023. If you are one of the few using this, see the migration guide.
⚠ Potentially breaking changes
run build before deploy (#7195)
The
deploycommand now runs the site's configuredbuildcommand before deployment by default. Previously, this was achieved by passing the--buildflag. In other words,--buildis no longer needed.To opt into the previous default behavior, users can now specify
netlify deploy --no-build.👉🏼 Why are we changing this?
This has long been one of the most common sources of confusion with the Netlify CLI. Developers expect a "deploy" command to deploy their project. We're making this change to follow the Principle of Least Surprise and streamline the experience for new users.
Upgrading
👉🏼 (most common) Build and deploy
Remove the
--buildflag:netlify deploy --build [...] # before→
netlify deploy [...] # after👉🏼 Separate build and deploy
Collapse into one command, if you can:
→
netlify deploy # afterOtherwise, add the
--no-buildflag:→
👉🏼 (rare) Deploy without build step
Add the
--no-buildflag:netlify deploy [...] # before (there was no `--build` here)→
polish and improve deploy command output (#7250) (795a451)
If you were automatically looking for specific strings in the
netlify deployoutput, your scripts may stop working. See the above PR for details.Note that this is not recommended and such changes may not be considered breaking in the future. For stable output that conforms to semantic versioning, use
netlify deploy --json.Features
netlify-lambdapackage (#7236) (0d48c28)Bug Fixes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.